Repository navigation
Conversation
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
|
The first CI run failed before reaching any test: the runner has no Generated by Claude Code |
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
…ist workers Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
… path no longer exists Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
|
CI status. This repo's test workflow had never passed on a PR, so I fixed what blocked it: missing One failure remains and is not from this PR: Generated by Claude Code |
…ilons, controller axis) Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
…_testing, shared workflows, AGENTS.md Remove the copies of the workflows (Test.yml, Testbase.yml) and call the reusable ones of pymodaq_plugins_template; add AGENTS.md and CLAUDE.md for AI coding assistants. This replaces the CI fixes made earlier on this branch to the copied workflow. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
…t of the package Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
The acceptance checks need one axis name per unit in _controller_units. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
pymodaq>=5.3.2, pymodaq_utils>=5.3.1, pymodaq_gui>=5.3.0, pymodaq_data>=5.3.0, so that the acceptance tests and the rest of this change are met at install time. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
2 participants
Before: the package had no extension, and there was no small, working example of a Dashboard extension driving instruments (the core ones are hundreds to thousands of lines).
After:
extensions/move_and_grab.py(about 130 lines,extensions = true): it picks an actuator and a detector of the Dashboard's experiment throughmodules_manager, moves the actuator to a target (aDataActuatorwith units), grabs the detector, shows the data in aViewerDispatcherand can save them to the h5 file. It never blocks the GUI (move and grab use callbacks, with a timeout handler), and refuses to quit while busy. The README lists it; the PyMoDAQ page "How a Dashboard extension works" (PyMoDAQ/PyMoDAQ#1296) explains the structure.How: tested with
tests/test_move_and_grab.py(5 tests: structure, instrument lists, move and grab with units and tolerance, quit refused while busy, saving into a temporary folder) against the mock actuator and the mock 0D detector of PyMoDAQ, offscreen with PySide6 6.12 and PyMoDAQ 5.3.2 (all pass locally). Not tested on real hardware, it only uses mock instruments.check_pluginreports nothing for the new module.🤖 Generated with Claude Code
https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg
Generated by Claude Code